-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Dataset Quality] Added Dataset Quality Locator #177000
[Dataset Quality] Added Dataset Quality Locator #177000
Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the types here will be removed as part of another ticket to make use of the types from the data plugin
https://github.com/elastic/kibana/blob/9e04d2c5c7b2139b7e23743b133ea79bf93f5ba3/src/plugins/data/common/query/timefilter/types.ts
const qualityCounts = mapPercentagesToQualityCounts(datasetsQuality.percentages); | ||
const datasetsWithoutIgnoredField = |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not part of the PR scope but a bug that is found and decided to fix it here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this file will later on be moved to the dataset quality plugin as we are planning to create our own app
): DatasetQualityLocatorParams => { | ||
const { time, refreshInterval } = logsExplorerState; | ||
const locatorParams: DatasetQualityLocatorParams = { | ||
filters: { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this construction will be refactored when we use the types from the data plugin
@@ -95,6 +96,10 @@ export class ObservabilityLogsExplorerPlugin | |||
useHash, | |||
}) | |||
); | |||
const datasetQualityLocator = share.url.locators.create( | |||
new DatasetQualityLocatorDefinition({}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are we not using useHash
here? What's the difference?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes correct will add it here we should read it from state:storeInSessionStorage
const pageState = datasetQualityUrlSchemaV1.urlSchemaRT.encode( | ||
deepCompactObject({ | ||
v: 1, | ||
filters, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here we will be not only taking into account timeRange or the other filters as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
at the moment I am only passing the timerange, its the only filter added to the locator params.
We can later add more filters to the interface
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀
💚 Build Succeeded
Metrics [docs]Module Count
Public APIs missing comments
Async chunks
Page load bundle
Unknown metric groupsAPI count
ESLint disabled line counts
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: |
This is a [follow up](#177000 (comment)) PR of #177000. ## Changes - Replace custom types for `timeRangeConfig` in dataset quality with common types coming from data plugin.
This is a [follow up](elastic#177000 (comment)) PR of elastic#177000. ## Changes - Replace custom types for `timeRangeConfig` in dataset quality with common types coming from data plugin.
closes elastic#170611 ## 📝 Summary This PR adds the infrastructure work for the locators needed to create the navigation link from the Logs Explorer to the Dataset Quality Page, but the links themselves are to be added with a later ticket. ## 💡For Reviewers To be abled to test this PR you can add the below code [here](https://github.com/elastic/kibana/blob/main/x-pack/plugins/observability_solution/observability_logs_explorer/public/components/logs_explorer_top_nav_menu.tsx#L150) to make the link visible in the Logs Explorer Page. `<ConnectedDatasetQualityLink /> <VerticalRule />` ## 🎥 Demo https://github.com/elastic/kibana/assets/11225826/1f3ce10a-3b8c-4027-b72d-1ed71b782fa5
This is a [follow up](elastic#177000 (comment)) PR of elastic#177000. ## Changes - Replace custom types for `timeRangeConfig` in dataset quality with common types coming from data plugin.
Pinging @elastic/obs-ux-logs-team (Team:obs-ux-logs) |
closes #170611
📝 Summary
This PR adds the infrastructure work for the locators needed to create the navigation link from the Logs Explorer to the Dataset Quality Page, but the links themselves are to be added with a later ticket.
💡For Reviewers
To be abled to test this PR you can add the below code here to make the link visible in the Logs Explorer Page.
<ConnectedDatasetQualityLink /> <VerticalRule />
🎥 Demo
datasetqualitynavigation.mov